The program fails to display `cout` when it is run?

Your program works fine on my system (Mandriva Linux 2010.1 64-bit) A common issue when developing simple programs doing text I/O in Windows is that the console (cmd. Exe) window where they are run will close on its own when the program terminates. That prevents the developer/user from being able to read the program's final output.

Perhaps this is what is happening in your case? EDIT: Confirmed on Visual Studio 2010. The window closes before you can read the output.

You can work around this issue if you either add system("pause") or just read an empty input line before the return statement. Keep in mind that the system("pause") trick" is Windows-specific and I do not recommend it, although it's slightly faster to type EDIT 2: I tried reading an empty input line and I realised that you may actually need to read two such lines, because you already have a remaining newline character in the input buffer that has not been retrieved by the last cin statement.

Your program works fine on my system (Mandriva Linux 2010.1 64-bit). A common issue when developing simple programs doing text I/O in Windows is that the console (cmd. Exe) window where they are run will close on its own when the program terminates.

That prevents the developer/user from being able to read the program's final output. Perhaps this is what is happening in your case? EDIT: Confirmed on Visual Studio 2010.

The window closes before you can read the output. You can work around this issue if you either add system("pause"); or just read an empty input line before the return statement. Keep in mind that the system("pause") "trick" is Windows-specific and I do not recommend it, although it's slightly faster to type.

EDIT 2: I tried reading an empty input line and I realised that you may actually need to read two such lines, because you already have a remaining newline character in the input buffer that has not been retrieved by the last cin statement.

Thanks for your feedback, thkala. – Jeff - FL Jan 15 at 18:49 Yes, I compiled/ran first. – Jeff - FL Jan 15 at 18:51 SilverbackNet - so I should highlight the brackets {} in bold?

Jim Lewis - I recompiled and ran the program several times. I believe what thkala mentioned: that the cmd. Exe window closes before program terminates.It could be the reason why.

– Jeff - FL Jan 15 at 18:59 @Jeff: Just FYI, StackOverflow has a notification system for comments, triggered by putting an "@" before the person's handle like I've done here. (First 3 characters of the handle is sufficient, I think.) But I'm not sure if multiple notifications in one comment work, so you might want to comment to each person separately. And welcome to SO!

– Jim Lewis Jan 15 at 19:09.

You could add another cin before the return statement to end the program after you view the ouptut. Thkala's logic is correct.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.